Generate nonsemantic shader debug information #1392
Conversation
|
Hey, we are also interested in this feature. Can someone look at this and merge it? |
There was a problem hiding this comment.
The code is good.
The policy question is that when using -g the downstream tools and driver have to undertand non-semantic extended instruction sets. So in theory it's a backward incompatibility. But this is about debug info and it's being used in a development environment so it has to be deliberately turned on, and the remedy is easy: turn it back off.
So I think this is the right thing to do, even with the theoretical incompatibility.
dneto0
force-pushed
the
non-semantic-shader-debug
branch
from
3e04b40 to
8768d60
Compare
|
Hi! Debug information is very useful for Vulkan-API debugging with RenderDoc. I hope it will be merged soon! :) |
|
Why hasn't this been merged? |
|
There are failing tests which need to be fixed up. The |
Proof of concept fix for #1391.
Possibly
emitNonSemanticShaderDebugInfoandemitNonSemanticShaderDebugSourceshould be controlled using dedicated command line arguments instead of just-g.This worked for me and allowed me to use RenderDoc source debugging.